Add cargo semver-checks to CI #1092
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Proof of concept to showcase: ProvableHQ/snarkVM#2912
You may want to cache the
targetfolder too like we do in that PR, where we get a speedup from from 40 minutes down to 15 minutes.By default checks are made against the most recent published release. The approach I take in snarkVM is to manually append a
--baseline-rev eff84712bif I want to just compare against a recent commit in between releases.